Anomaly Metrics

• Page views: You can investigate page views anomalies by looking at your traffic analytics tool to pinpoint what the problem might be.

• JavaScript errors: JavaScript error anomalies are usually caused by third parties, user paths, and code errors. They can also be caused by a new campaign, A/B testing, or ad technology. See Anomaly Example: JavaScript Errors.

• Resource count: Resources are anything that renders on the page (for example, CSS, JavaScript, fonts, images, videos, and so on). The anomaly alert tells you on which page the resource count anomaly occurred and whether the resource count changed for any specific third party. Resource count anomalies are rare. They usually occur after events like a site redesign.

Yottaa collects anomaly metrics about violations, including: 

• All violations

• Page Delay violations

• Size violations

Use the Violations and JavaScript Errors dashboard to investigate violations anomalies. For more about the different types of violations, see Violations .